wayland: Avoid using uninitialized memory
authorMatthias Clasen <mclasen@redhat.com>
Thu, 18 Apr 2019 14:22:48 +0000 (14:22 +0000)
committerMatthias Clasen <mclasen@redhat.com>
Thu, 18 Apr 2019 14:27:00 +0000 (14:27 +0000)
commitecdad20827503ee9beb24f90351dc5588fbb3ed0
tree4d70d7a18eb943266c0def100a72816a0c79c59b
parent5cd8e0f7f18cdd6de6482b9cdae14bd5b0819c73
wayland: Avoid using uninitialized memory

_gdk_wayland_cursor_get_buffer was not initializing
its out variables in the 'not found' case. This
was showing up in protocol traces as garbage hotspots
being sent to the compositor.

Closes: https://gitlab.gnome.org/GNOME/gtk/issues/1328
gdk/wayland/gdkcursor-wayland.c